5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
- Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-3: Specifying Statements

Universal Data Formats


Each of the four basic data types has its own universal format which is used for specifying constants within ILF statement and is described below:

A numeric constant consists of digits, an optional decimal point, an optional trailing or leading minus sign, or a blank for a null entry. A plus sign is implied for positive numbers but is not allowed as a symbol. Currency signs, such as $, are not allowed.

A date/time constant consists of a mandatory series of 16 digits (or hyphens, as described below), or a blank for a null entry. The 16 digits incorporate eight sets of two digits each that represent, from left to right, century, year, month, day, hour, minute, second, and hundreds of a second. To indicate that a particular part of a complete date/time format should be ignored in a comparison or operation, you can enter a pair of hyphens in the appropriate positions. For example, you would enter December 31st as '----1231--------'.

An alphanumeric constant consists of any combination of letters, numbers, and special characters. Leading, embedded, or trailing spaces are allowed. Leading and embedded spaces are treated as significant for comparison purposes.

A logic constant is one that contains the answer to a 'yes/no' question, such as, 'Is this a domestic customer?' The valid values for a logic-type field within an ILF statement are:

The number 1 or the letter Y is equivalent to yes or affirmative or .

The number 0 or the letter N is equivalent to no or negative or .

A blank (space) is equivalent to an unknown response or . It means the answer is not known or that the field value is not filled in yet.

Application Design Manual                                         "Powered by Appx Software"

558

©2006 By APPX Software, Inc. All Rights Reserved